Skip to content

Comments

Validate proposal data on update endpoint#611

Merged
valentin0h merged 2 commits intodevfrom
validate-proposal-on-update
Feb 18, 2026
Merged

Validate proposal data on update endpoint#611
valentin0h merged 2 commits intodevfrom
validate-proposal-on-update

Conversation

@valentin0h
Copy link
Collaborator

@valentin0h valentin0h commented Feb 16, 2026

Following #604, now updating the update proposal handler to validate against the schema.

@vercel
Copy link
Contributor

vercel bot commented Feb 16, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
app Ready Ready Preview Feb 18, 2026 3:54am

Request Review

data.proposalData,
if (data.proposalData) {
const instanceData =
processInstance.instanceData as DecisionInstanceData | null;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to type this since we asserted earlier?

Extract validateProposalAgainstTemplate to DRY up the collab-doc-aware
validation logic shared by submitProposal and updateProposal. The update
endpoint now uses resolveProposalTemplate (checking both instanceData and
processSchema) instead of only reading processSchema directly.
@valentin0h valentin0h merged commit 0256c41 into dev Feb 18, 2026
10 checks passed
@valentin0h valentin0h deleted the validate-proposal-on-update branch February 18, 2026 04:01
@scazan scazan mentioned this pull request Feb 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants